Exchange server 2010 was installed on a addtional server in our enviroment all mailboxes and public folders where moved from our SBS 2003 Exchange server DC all mail is flowing properly in 2010 enviroment. The Exchange 2003 is located on a SBS 2003 we are migating to a Standand server enviroment and decommsioning SBS 2003, a 2008R2 domain controller is already up and functioning properly. I uninstalled Exchange 2003 server on the SBS and as a result the Exchange 2003 Message and Colaberation services were not removed. All other Exchange componets were removed and this was left behind as an uninstall error. In addtion the services.msc applet on the 2003 SBS is still showing several Exchange services. (pop connector, Information store, exchange mangement, mta stacks, exchange system attendent) . They obviously will not start as all the Exchange files were removed during uninsall. The Message and Colaberation services failed on removal during schema update phase of the uninstall at which time I clicked canel and it proceded with the remainder of the uninstall. I plan on demoting the SBS2003 from a DC and removing from the network so not really concerned about the lingering services showing on that box. Will the Exchange 2003 Message and Colaberation services not being removed cause any future issues or should it be removed manually from the schema or some other method? Any help would be greatly appreciated

I would prefer to have graceful removal which will happen if you properly do the uninstallation steps. If no options are left out, try manual removal through ADSIEDIT. http://support.microsoft.com/kb/833396Shaba

Hello Agree with Shabarinath you can remove the Legacy Exchange from ADSI Edit but make sure you dont have any Mailboxes or service running for your org. Best way is to shutdown the server and monitor the Mailflow or Services then remove it from ADSI edit. Thanks Mouzzam Hussain Visit to my Blog mouzzamh.wordpress.com

I have seen this happen loads of times. Usually reinstalling Exchange using the CD-ROM/installation files and selecting the reinstall option, saying "no" to all the prompts about file version mismatches, then removing the product again resolves the issue. It comes out clean that way. Rarely do I have to go to adsiedit to remove the server, I don't think I have had to for at least six months (and I have removed a lot of servers in that time). Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Ok thanks for the replies I will give Simon's reinstall solution a try before atempting to remove with adsiedit Thanks Dennis

Tried the reinstall and answering no to file overwrites and then removed Exchange 2003 Got error "problem with Exchange message and colaboration setup" "Setup is canceling" Guess next step will be manual uninstall? Thanks --Dennis

Has the machine been gutted of everything else? AV, Backup software, antispam etc? All of those can have hooks in Exchange which can stop a successful uninstall. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

It is SBS 2003 Server SP2 and it does have Symantec corp edtion AV installed. I can totaly disable this and try again not really any other 3rd party software on the box. Could not having SBS SP1 installed be causing the issue? The reinstall of Exch went fine it is the uninstall giving me grief. Do you think a manual uninstall will cause any future issues? I really apreciate all your help Thanks --Dennis

If there is a Symantec product on the server then I have a simple rule - that is the cause of the problem. Disabling it is not enough, you need to remove it and reboot the server to get its hooks out of the system. So remove the Symantec junk, reboot and then try the uninstall again. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

If there is a Symantec product on the server then I have a simple rule - that is the cause of the problem. Disabling it is not enough, you need to remove it and reboot the server to get its hooks out of the system. So remove the Symantec junk, reboot and then try the uninstall again. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Removed all the Symantec and still same issue. Decided to do the manual uninstall and all appears well. Powershell get-exchangeserver now only showing my 2010. SBS DC demotion and roles transfer was successfull, now all R2 with clean event logs. Thanks for everyones help with this issue Dennis